Medical Communication Hub and Associated Methods

ABSTRACT

A patient communication system having a medical sensing device operable to collect medical data, a network communication module operable to transmit the medical data onto a data network, a controller operable route the first medical sensing data to the network communication module, and a power source operable to provide power to the first medical sensing device, the controller, and the network communication module.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 14/238,026, filed Feb. 10, 2014, which is a U.S. national stageapplication Patent Cooperation Treaty Application No. PCT/US2012/052241,filed Aug. 24, 2012, which claims priority to and the benefit of U.S.Provisional Patent Application No. 61/526,990, filed Aug. 24, 2011, eachof which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to the field ofmedical devices and, more particularly, to a medical communicationsystem and associated methods of use.

BACKGROUND

Innovations in diagnosing and verifying the level of success oftreatment of disease have migrated from solely using external imagingprocesses to now including internal diagnostic processes as well. Inparticular, diagnostic equipment and processes have been developed fordiagnosing vasculature blockages and other vasculature disease by meansof ultra-miniature sensors placed upon the distal end of a flexibleelongate member such as a catheter, or a guide wire used forcatheterization procedures. For example, known medical sensingtechniques include angiography, intravascular ultrasound (IVUS), forwardlooking IVUS (FL-IVUS), fractional flow reserve (FFR) determination, acoronary flow reserve (CFR) determination, optical coherence tomography(OCT), trans-esophageal echocardiography, and image-guided therapy. Eachof these techniques may be better suited for different diagnosticsituations. To increase the chance of successful treatment, health carefacilities may have a multitude of imaging and sensing modalities onhand in a catheter lab during a procedure. However, each imagingmodality in a catheter lab traditionally requires its ownspecial-purpose diagnostic equipment. For instance, an imaging modalitymay require a catheter, a patient interface module (PIM), a user controlinterface, a display, a specialized power unit, and a processing unitsuch as a customized personal computer. Traditionally, all of thisequipment is located in the catheter room itself during a procedure anddepends on a substantial wiring infrastructure for data transport anddependable power. Physical space is typically at a premium in catheterlabs and each additional imaging modality employed in a catheter labcomplicates the pre-procedure setup and limits the movement of healthcare professionals during procedures. For example, typically, eachadditional imaging modality may require its own communication cable andits own power cable. These cable assemblies are often coiled underpatient tables and are prone to being damaged from either being steppedon by personnel or equipment rolling over them. Cleaning the cablesafter a procedure is also very time consuming and difficult.

While the existing devices and methods have been generally adequate fortheir intended purposes, they have not been entirely satisfactory in allrespects. The medical sensing systems and associated methods of thepresent disclosure overcome one or more of the shortcomings of the priorart.

SUMMARY

In one exemplary aspect, the present disclosure is directed to a poweredmedical communication hub. The hub includes a housing and a rearinterface assembly disposed at a distal end of the housing. The rearinterface assembly includes a first data link configured to transmitfirst medical data associated with a first modality to a processingsystem and a power link configured to receive a first amount of power.The hub also includes a power distribution module disposed within thehousing, electrically coupled to the power link, and configured toconvert the first amount of power into a plurality of power levels, anda forward interface assembly disposed at a proximal end of the housing,the forward interface assembly including a first connectorcommunicatively coupled to the first data link and electrically coupledto the power distribution module, the first connector being configuredto provide a first medical sensing device coupled thereto with a secondamount of power equal to one of the plurality of power levels andreceive the first medical data from the first medical sensing device.

In some instances, the housing may be fluid resistant and an interfacebetween the rear interface assembly and the housing and an interfacebetween the front interface assembly and the housing may be fluidresistant. Also, in some instances, the second amount of power may bedifferent than the first amount of power. Additionally, in someinstances, the front interface assembly may include a second connectorelectrically coupled to the power distribution module, the secondconnector being configured to provide a second medical sensing devicecoupled thereto with a third amount of power equal to one of theplurality of power levels and receive second medical data associatedwith a second modality different from the first modality from the secondmedical sensing device.

In another exemplary aspect, the present disclosure is directed to amedical communication system including a powered medical communicationhub having a mounting portion thereon. The hub includes a plurality ofconnectors, each connector in the plurality of connectors beingconfigured to receive medical data associated with a different medicalsensing modality and to provide power to a medical sensing devicecoupled thereto and a rear interface assembly configured to receive aplurality of cables, the cables communicatively and electricallycoupling the hub to a processing system. The system also includesmounting means releaseably coupled to the mounting portion of thepowered medical communication hub, the mounting means being configuredto mount the powered medical communication hub within a medicalenvironment and a cable protection assembly releaseably coupled to therear interface assembly of the powered medical communication hub, theplurality of cables extending through the cable protection assembly.

In some instances, the cable protection assembly may include an elongateand flexible housing enclosing the cables therein. Also, in otherinstances, the mounting means may include a rail clamp configured toreleaseably couple to a rail in a medical environment. In yet anotherexemplary aspect, the present disclosure is directed to a method ofcollecting medical sensing data including receiving, at a poweredmedical communication hub, a first amount of power from a power source,converting, with a power distribution module in the powered medicalcommunication hub, the first amount of power into a plurality of powerlevels, providing, with the powered medical communication hub, a secondamount of power equal to one of the plurality of power levels to a firstmedical sensing device, receiving, at the powered medical communicationhub, first medical data associated with a first modality from the firstmedical sensing device, and transmitting, with the powered medicalcommunication hub, the first medical data to a processing system.

In some instances, the method of collecting medical sensing data mayinclude providing, with the powered medical communication hub, a thirdamount of power equal to one of the plurality of power levels to asecond medical sensing device, receiving, at the powered medicalcommunication hub, second medical data associated with a second modalitydifferent from the first modality from the second medical sensingdevice, and transmitting, with the powered medical communication hub,the second medical data to the processing system.

In one exemplary aspect, the present disclosure is directed to a patientcommunication system. The patient communication system includes a firstmedical sensing device operable to collect first medical data associatedwith a first modality and an analog to digital converter communicativelycoupled to the first medical sensing device and operable to digitize thefirst medical data. The system also includes a network communicationmodule communicatively coupled to the first medical sensing device and adata network, the network communication module operable to transmit thedigitized first medical data onto the data network. Further, the systemincludes a controller communicatively coupled to the analog to digitalconverter and the network communication module and operable route thefirst medical sensing data to the network communication module. Thesystem also includes a power source operable to provide power to thefirst medical sensing device, the controller, and the networkcommunication module.

In some instances, the patient communication system includes including ahub having therein the analog to digital converter, controller, andnetwork communication module. Further, in some instances, the systemincludes a first patient isolation module communicatively coupled to thefirst medical sensing device and the hub and operable to receive thefirst medical data from the first medical sensing device and transmitthe first medical data to the hub, the first patient isolation modulebeing further operable to route power from the power source to the firstmedical sensing device.

In another exemplary aspect, the present disclosure is directed to amethod of collecting medical sensing data. The method of collectingmedical sensing data includes collecting, with a first medical sensingdevice, first medical data associated with a first modality anddigitizing, with an analog to digital converter, the first medical data.The method also includes routing, with a controller communicativelycoupled to the analog to digital converter, the digitized first medicaldata to a network communication module and transmitting, with thenetwork communication module communicatively coupled to a data network,the digitized first medical data onto the data network. Further themethod includes providing power, with a power source, to the firstmedical sensing device, the controller, and the network communicationmodule.

In some instances, the digitizing with the analog to digital converter,the routing with the controller, the transmitting with the communicationmodule, and the providing power with the power source are performed by ahub communicatively coupled to the first medical device. Further, insome instances, the collecting first medical data includes transmittingthe first medical data through a first patient isolation module to thehub.

In another exemplary aspect, the present disclosure is directed to apatient communication system. The patient communication system includesa first control module operable to receive first medical data associatedwith a first modality from a first body sensing device and a secondcontrol module operable to receive second medical data associated with asecond modality from a second body sensing device. The system furtherincludes a first power module operable to dynamically supply a firstamount of power to the first body sensing device based on a powerrequirement of the first body sensing device and a second power moduleoperable to dynamically supply a second amount of power to the secondbody sensing device based on a power requirement of the second bodysensing device. Further, the system includes a communication moduleoperable to transmit the first and second medical data to a datanetwork.

In another exemplary aspect, the present disclosure is directed to amethod of using a patient communication system. The method of using apatient communication system includes coupling a first body sensingdevice to a first patient isolation module, the first body sensingdevice including a first sensor disposed thereon and coupling the firstpatient isolation module to a hub, the hub communicatively coupled to adata network. The method further includes coupling a second body sensingdevice to a second patient isolation module, the second body sensingdevice including a second sensor disposed thereon and coupling thesecond patient isolation module to the hub. Further, the method includesutilizing the first sensor to collect first medical characteristic dataassociated with a patient, the collecting including transmitting thefirst medical characteristic data to the hub and also utilizing thesecond sensor to collect second medical characteristic data associatedwith the patient, the collecting including transmitting the secondmedical characteristic data to the hub. The method also includestransmitting, with the hub, the first and second medical characteristicdata to the data network and receiving, at a user interface, processedfirst and second medical characteristic data from the data network, theuser interface being communicatively coupled to the hub.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic drawing depicting a medical sensing communicationsystem including a powered medical communication hub according to oneembodiment of the present disclosure.

FIG. 2A is a diagrammatic front perspective view of the powered medicalcommunication hub of FIG. 1 installed in a catheter lab.

FIG. 2B is a diagrammatic front close-up view of the powered medicalcommunication hub of FIG. 1.

FIG. 3 is a diagrammatic rear perspective exploded view of portions ofthe powered medical communication hub of FIG. 1.

FIG. 4 is a rear perspective view of a powered medical communication hubwith an angled coupler attached thereto.

FIG. 5 is a rear perspective view of a powered medical communication hubwith a straight coupler attached thereto.

FIG. 6 is a diagrammatic front perspective view of an aspect of amedical communication system installed in a medical environment.

FIG. 7 is a diagrammatic perspective view of a horizontal rail mount.

FIG. 8 is a diagrammatic perspective view of a vertical rail mount.

FIG. 9 is a diagrammatic perspective view of a magnetic mounting system.

FIG. 10 is a diagrammatic perspective view of an angled mountingbracket.

FIG. 11A is a front view of a powered medical communication hub in afluid-resistant configuration.

FIG. 11B is a diagrammatic sectional side view of a connector on a frontpanel of the powered medical communication hub of FIG. 11A.

FIG. 11C is a diagrammatic perspective view of a protective capaccording to various aspects of the present disclosure.

FIG. 12 is a functional block diagram of an embodiment of a poweredmedical communication hub.

FIG. 13 is a functional block diagram of a further embodiment of apowered medical communication hub.

FIG. 14 is a schematic drawing depicting a medical sensing communicationsystem including a bedside utility box according to one embodiment ofthe present disclosure.

FIG. 15 is a diagrammatic perspective view of the bedside utility box ofFIG. 1.

FIG. 16 is a functional block diagram of an embodiment of a bedsideutility box.

FIG. 17 is a functional block diagram of an aspect of the medicalsensing communication system that includes a software frameworkexecuting on a bedside utility box.

FIG. 18 is a schematic drawing depicting a medical sensing communicationsystem according to another embodiment of the present disclosure.

FIG. 19 is a functional block diagram of an exemplary embodiment of anaspect of the medical sensing communication system of FIG. 18,specifically, a patient isolation module.

DETAILED DESCRIPTION

For the purposes of promoting an understanding of the principles of thepresent disclosure, reference will now be made to the embodimentsillustrated in the drawings, and specific language will be used todescribe the same. It will nevertheless be understood that no limitationof the scope of the disclosure is intended. Any alterations and furthermodifications in the described devices, instruments, methods, and anyfurther application of the principles of the disclosure as describedherein are contemplated as would normally occur to one skilled in theart to which the disclosure relates. In particular, it is fullycontemplated that the features, components, and/or steps described withrespect to one embodiment may be combined with the features, components,and/or steps described with respect to other embodiments of the presentdisclosure.

FIG. 1 is a schematic drawing depicting a medical sensing communicationsystem 100 including a powered medical communication hub 101. Themedical sensing communication system 100 is a data collection solutionfor multiple modality medical sensing. Generally, in the system 100, thehub 101 is a central unit that connects to a plurality of medicalsensing-related tools, distributes power to the plurality of tools, andfacilitates communication between the tools and a processing workstationand/or data network. In one embodiment, the communication system 100 maybe utilized to collect data from medical sensing devices and transmit itto computing resources, where it is processed and returned.

In the illustrated embodiment, the medical sensing communication system100 is deployed in a catheter lab 102 having a separate control room 104isolated by an intervening wall 105. In other embodiments, however, themedical sensing communication system 100 may be deployed in an operatingroom, diagnostic room, or other medical environment used to perform anynumber of patient procedures. The catheter lab 102 includes a sterilefield but its associated control room 104 may or may not be steriledepending on the requirements of a procedure and/or health carefacility. The catheter lab and control room may be used to perform on apatient any number of medical sensing procedures such as angiography,intravascular ultrasound (IVUS), virtual histology (VH), forward lookingIVUS (FL-IVUS), intravascular photoacoustic (IVPA) imaging, a fractionalflow reserve (FFR) determination, a functional measurementdetermination, a coronary flow reserve (CFR) determination, opticalcoherence tomography (OCT), computed tomography, intracardiacechocardiography (ICE), forward-looking ICE (FLICE), intravascularpalpography, transesophageal ultrasound, or any other medical sensingmodalities known in the art. For example, in catheter lab 102 a patient106 may be undergoing a multi-modality procedure, in which IVUS datawill be collected with an IVUS catheter 108 and OCT data will becollected with an OCT catheter 110. The IVUS catheter 108 may includeone or more sensors such as a phased-array transducer. In someembodiments, the IVUS catheter 108 may be capable of multi-modalitysensing such as IVUS and IVPA sensing. The OCT catheter 110 may includeone or more optical sensors.

The communication system 100 includes a number of interconnected medicalsensing-related tools in the catheter lab 102 and control room 104 tofacilitate this multi-modality workflow procedure, including an IVUSpatient interface module (PIM) 112, an OCT PIM 114, an electrocardiogram(ECG) device 116, a bedside control surface 118, a processing system120, and a boom display 122. The hub 101 in the catheter lab 102consolidates the multitude of cables extending from these medicalsensing-related tools and communicatively couples them to the processingsystem 120. That is, the hub 101 is an intermediary through which thetools in the catheter lab 102 connect to the processing system 120. Ingeneral, the hub 101 is coupled to the processing system 120 via aplurality of power and communication cables. To alleviate the problemsassociated with loose cabling in a crowded medical working environment,the cables coupling the hub 101 to the processing system 120 extendthrough a protective hose 124 and a trench 126 in the floor of thecatheter lab 102. The cables enter the trench 126 through a trench entryport 128. In this manner, the cables are aggregated and protected theentirety of the distance from the hub 101 to the processing system 120.Of course, the cabling between the hub 101 and processing system 120 maybe oriented in many other configurations depending on the specificcatheter lab configuration. For instance, the cabling may extend throughthe protective hose 124 and enter a wall or a ceiling through atermination plate before travelling to the processing system. In theillustrated embodiment, the hub 101 is mounted on the floor near thepatient 106 to reduce the amount of cabling located in high-trafficareas near the patient. In some instances, the hub 101 may be located inthe sterile field surrounding the patient 106. The hub 101 and itsassociated cabling and mounting solutions will be described in greaterdetail in association with FIGS. 2-12.

In the illustrated embodiment, the processing system 120 is a computerworkstation with the hardware and software to acquire, process, anddisplay multi-modality medical sensing data, but in other embodiments,the processing system 120 may be any other type of computing systemoperable to process medical data or assist in computer aided surgery(CAS). In the embodiments in which processing system 120 is a computerworkstation, the system includes at least a processor such as amicrocontroller or a dedicated central processing unit (CPU), anon-transitory computer-readable storage medium such as a hard drive,random access memory (RAM), and/or compact disk read only memory(CD-ROM), a video controller such as a graphics processing unit (GPU),and a network communication device such as an Ethernet controller. U.S.Patent Application No. 61/473,570, entitled “MULTI-MODALITY MEDICALSENSING SYSTEM AND METHOD”, discloses a computing resource capable ofprocessing multi-modality medical sensing data and is herebyincorporated by reference in its entirety.

As mentioned above, the ECG device 116 is also communicatively coupledto hub 101 via a wired or wireless connection. The ECG device 116 isoperable to transmit electrocardiogram signals from patient 106 to thehub 101. In some embodiments, the hub 101 may be operable to synchronizedata collection with the catheters 108 and 110 using the ECG signalsfrom the ECG 116.

The bedside control surface 118 is also communicatively coupled to thehub 101 and provides user control of the particular medical sensingmodality (or modalities) being used to diagnose the patient 106. In thecurrent embodiment, the bedside control surface 118 is a touch screenthat provides user controls and diagnostic images on a single surface.In alternative embodiments, however, the bedside control surface 118 mayinclude both a non-interactive display and separate controls such asphysical buttons and/or a joystick. In the illustrated embodiment, thebedside control surface 118 and hub 101 communicate over a wiredconnection such as a standard copper link but, alternatively, thecontrol surface 118 and hub 101 may communicate wirelessly. The bedsidecontrol surface 118 includes an integrated processing unit to drive agraphical user interface (GUI)-based workflow presented on the touchscreen. U.S. Patent Application No. 61/473,591, entitled “DISTRIBUTEDMEDICAL SENSING SYSTEM AND METHOD” and filed on Apr. 8, 2011 underattorney docket number 44755.784, discloses a bedside control surfacethat executes GUI-based workflows using a software framework and ishereby incorporated by reference in its entirety.

The system 100 further includes a boom display 122. The boom display 122may include one or more monitors capable of displaying informationassociated with a medical sensing procedure. In the illustratedembodiment, the boom display 122 is coupled to, powered, and driven bythe hub 101.

With reference now to FIGS. 2A, 2B, and 3, illustrated is an aspect ofthe medical sensing communication system 100. Specifically, FIG. 2A is adiagrammatic front perspective view of the powered medical communicationhub 101 of FIG. 1 installed in a medical environment such as catheterlab 102, and FIG. 2B is a diagrammatic front close-up view of the hub101. FIG. 3 is a diagrammatic rear perspective exploded view of portionsof the hub 101. As mentioned above, the hub 101 is a intermediarythrough which the medical sensing-related tools receive power andcommunicate with processing system 120. In one general aspect, the hub101 is operable to provide power and instructions to medical sensingdevices and transfer medical sensing data from connected medical sensingdevices such as the IVUS PIM 112 and OCT PIM 114 to remote computingresources such as processing system 120 to be processed. Once processed,the medical sensing data may be returned to the hub 101, where it isrouted to the control surface 118 and boom display 122 to be displayedand analyzed by clinicians.

The hub 101 includes a cylinder-like housing 200. In the illustratedembodiment, the housing 200 is constructed of a impact-resistant andfluid-resistant metal and has a height of approximately 3.5 inches, awidth of approximately 10 inches, and a depth of approximately 8 inches.In alternative embodiments, the housing 200 may be constructed of adifferent suitable material and/or be of different dimensions. Thehousing 200 includes a bottom mounting surface 202 and a top mountingsurface 204, both of which are planar. The bottom mounting surface 202includes a set of threaded mounting apertures 206 and the top mountingsurface 204 includes a set of threaded mounting apertures 208. As willbe described in association with FIGS. 7-10, any number of mountingbrackets may be releaseably coupled to the housing 200 using either setof threaded mounting apertures 206 and 208. In the illustratedembodiment, each set of mounting apertures is configured to conform tothe Video Electronics Standards Association (VESA) MIS-D hole mountpattern. In alternative embodiments, the mounting apertures 206 and 208may conform to a different standard or may conform to a proprietarypattern. Further, the mounting surfaces 202 and 204 may alternativelyinclude different mounting solutions such as channels, slots, clips, ormagnetic elements.

The hub 101 further includes a front interface panel 210 coupled to thefront of the housing 200 and a rear interface panel 212 coupled to therear of the housing 200. Each of the interface panels 210 and 212includes a complementary gasket 213 disposed on the side facing thehousing 200 such that when they are secured to the housing 200 as shownin FIG. 2A they create a fluid-resistant seal. The gaskets 213 may beformed of rubber, silicone, or other sealing material. In oneembodiment, the hub 101 may have a rating of IPX4 against fluid ingressas defined by the International Electrotechnical Commission (IEC)standard 60529. In other embodiments in which the hub may be used indifferent environments, the hub may have a different fluid ingressrating. As shown in FIG. 3, the rear interface panel 212 includes acable aperture 214 through which cables extending from the hub 101 tothe processing system 120 may pass. As shown in FIG. 2B, the frontinterface panel 210 of the hub 101 includes a plurality of connectors towhich a plurality of medical sensing-related tools may connect. In theillustrated embodiment, the front panel 210 includes: an IVUS PIMconnector 220 with conductive contacts configured to transfer power,ground, data, and control signals; a functional measurement (FM) toolconnector 222 with conductive contacts configured to transfer power,ground, data and control signals; an first fiber optic connector 224 anda second fiber optic connector 226 each configured to pass power,ground, and light-based data signals; an OCT PIM connector 228 withconductive contacts configured to transfer 48 volts DC, ground, andEthernet-based data; a bedside control surface connector 230 withconductive contacts configured to transfer 12 volts DC, ground, andEthernet-based data; a FLIVUS PIM connector 232 with conductive contactsconfigured to transfer 48 volts DC, ground, and Universal Serial Bus(USB)-based data; and a FLIVUS footswitch connector 234 with conductivecontacts configured to transfer foot-actuated control signals. Theconnectors 220, 222, 228, 230, 232, and 234 are push-pull ring styleconnectors that are configured to allow for one-handed connection anddisconnection of cables. Further, the connectors are fluid-resistant(sealed), color-coded for easy identification, and keyed differently,for example in shape and pin-count, so as prevent misconnected cables.For example, as shown in FIG. 2B, the FM tool connector includes 18 pinholes in a circular configuration, but the bedside control surfaceconnector includes 12 pin holes in a linear configuration. In theillustrated embodiment, the connectors 228, 230, 232, and 234 are JBXseries connectors commercially available from Souriau SAS of Versailles,France. However, in alternative embodiments, othercommercially-available or proprietary connectors may be utilized and theconnectors may be configured to include any number of additionalfeatures. Although the connectors 220, 222, 224, 226, 228, 230, 232, and234 as-labeled are associated with specific modalities, it iscontemplated that medical tools associated with additional and/ordifferent modalities may connect to one or more of the connectorsprovided that the medical tools' connectors are compatible (i.e. numberof pins, shape).

The front panel 210 further includes an auxiliary power connector 236configured to provide 24 volts DC, a ECG/aortic device connector 238,two USB connectors 240, and a VGA display connector 242. In one catheterlab configuration, the auxiliary power connector 236 may provide powerand the VGA display connector 242 may provide a video signal to abedside display monitor such as the boom display 122. Further, the USBconnectors 240 may couple to and receive control signals from bedsidecontroller devices such as joysticks, touchpads, hand gesture/motioncapture input devices, or any other suitable controller devices. In theillustrated embodiment, because the USB connectors 240 and the VGAdisplay connector 242 are standardized, it is contemplated that anynumber of USB-based and VGA-based tools may communicate with theprocessing system 120 via the hub 101. Additionally, the USB connectors240 may be fluid-resistant. Further, in alternative embodiments, the VGAdisplay connector 242 may be another type of display connector such as aDVI connector, an HDMI connector, a DisplayPort connector, an S-Videoconnector, or other video-based connector, and the USB connectors 240may be other types of data ports such as IEEE 1394 (FireWire),Thunderbolt, serial, parallel, eSATA, or proprietary connectors.Additionally, the front panel 210 includes an LED indicator 244configured to indicate when the hub 101 is powered on. The frontinterface panel 210 and the connectors 220, 222, 224, 226, 228, 230,232, 234, 236, 238, 240, and 242 may together be considered a forwardinterface assembly.

As mentioned above, FIG. 2A shows the hub 101 installed in one exampleconfiguration in a medical environment such as catheter lab 102.Specifically, a vertical mounting bracket 250 is coupled to the topmounting surface 204 via the set of threaded mounting apertures 208. Themounting bracket 250 is in turn mounted to a floor stand 252, which isconfigured to sit on the floor of a catheter lab with a plurality ofstabilizing feet. Further, cables extending from the hub 101 to theprocessing system 120 exit the hub 101 through the aperture 214 in therear panel 212 and extend through an angled coupler 254, the flexibleprotective hose 124, a second angled coupler 256, and an aperture in atermination plate 258. The angled coupler 254 releaseably couples to therear panel 212 and includes a rubber seal around its periphery such thatwhen it is coupled to the panel the interface between the coupler andthe panel is fluid-resistant. The flexible protective hose 124 isconfigured to protect the cables extending therethrough and may beresistant to bodily fluids and cleaning chemicals typically found inmedical environments. The flexible protective hose 124 is furtherpliable such that it may be routed in a convenient manner in a catheterlab. The termination plate 258 includes an aperture sized toapproximately match the diameter of the second angled coupler 256, andalso includes a set of mounting apertures 260 configured in astandardized pattern on the face of the plate. The mounting apertures260 permit the plate 258 to be mounted around an aperture (e.g. a wallexit point, floor exit point, etc) through which the hub-connectedcables exit the catheter lab. In the illustrated embodiment, thetermination plate 258 and the set of mounting apertures 260 conform tothe GE Termination standard. However, in other embodiments, thetermination plate 258 and apertures 260 may conform to another standardsuch the Phillips Termination standard, the double gang standard, or thesingle gang standard. As shown in FIG. 3, a straight coupler 262 mayalso be releaseably coupled to the rear panel 212 and the flexibleprotective hose 124. The straight coupler 262 directs the protectivehose 124 away from the hub 101 at a different angle than the angledcoupler 254 to provide for additional placement options in a catheterlab or other medical environment. The angled coupler 254 or straightcoupler 262, flexible protective hose 124, and second angled coupler 256may together be considered a cable protection assembly.

With reference now to FIGS. 4 and 5, illustrated are differentconfigurations of the medical communication system 100 in a medicalenvironment. Specifically, FIG. 4 is a rear perspective view of the hub101 with the angled coupler 254 coupled to the rear panel 212, and FIG.5 is a rear perspective view of the hub 101 with the straight coupler262 coupled to the rear panel 212. As shown by FIGS. 4 and 5, thecouplers 254 and 262 direct the flexible protective hose 124 away fromthe hub 101 at different angles. As shown, all cable-based connectionsto the rear of the hub 101 including power and communications arecontained within the flexible hose 124. Examples of the cables exitingthe rear of the hub 101 within the hose 124 are shown in FIG. 12.

FIG. 6 is a diagrammatic front perspective view of an aspect of themedical communication system 100 installed in a medical environment.Specifically, the hub 101 is mounted to the floor stand 252 and flexibleprotective hose 124 extends from the rear panel 212 to a straightcoupler 600 which is coupled to the trench entry port 128. In someembodiments, the trench entry port 128 includes a second aperture (notshown) disposed on the side opposite of the straight coupler 600. Thissecond aperture may be used to pass additional cables from the catheterlab into the trench below.

With reference now to FIGS. 7-10, illustrated are four mounting bracketsthat may be coupled to the hub 101 so that the hub may be dynamicallymounted in a medical environment such as catheter lab 102. FIG. 7 is adiagrammatic perspective view of a horizontal rail mount 700. Thehorizontal rail mount 700 includes a mounting surface 702 that isconfigured to couple to either the bottom mounting surface 202 or thetop mounting surface 204 on the hub 101. The mounting surface 702includes a set of mounting apertures that align with either the set ofmounting apertures 206 or 208 on the hub 101. In the illustratedembodiment, the set of mounting apertures on the mounting surface 702conforms to the VESA hole mount pattern, but, alternatively, may beconfigured to conform to a different pattern depending on the patternimplemented on the mounting surfaces of the hub 101. When the mountingapertures on the mounting surface 702 are aligned with either the set ofmounting apertures 206 or 208 on the hub 101, connectors such as screwsnay pass through the aligned apertures and releaseably couple thehorizontal rail mount 700 to the hub 101. The horizontal rail mount 700further includes a rail clamp 704 that is configured to releaseablycouple to a rail on or near a patient table in a catheter lab. In theillustrated embodiment, the rail clamp 704 is physically configured tomate with a standardized rail, and when the clamp is so mated, theattached hub 101 will be in a horizontal position. FIG. 8 is adiagrammatic perspective view of a vertical rail mount 800 that isconfigured to be coupled to the hub 101. Specifically, the vertical railmount 800 is similar to the horizontal rail mount 700 in that it has amounting surface 802 with a set of standardized mounting apertures and arail clamp 804. However, when the hub 101 is coupled to the mountingsurface 802 and the rail clamp 804 is clamped to a patient table rail,the hub 101 will be in a vertical position.

FIG. 9 is a diagrammatic perspective view of a magnetic mounting system900 configured to allow the hub 101 to be mounted in a variety oflocations around a catheter lab. The mounting system 900 includes amagnetic mount plate 902 with magnets disposed therein. The magneticmount plate 902 is configured to releaseably couple to either the bottommounting surface 202 or the top mounting surface 204 on the hub 101 viaa set of mounting apertures that align with the mounting apertures onthe hub. The magnetic mounting system 900 further includes a receiverplate 904 that may be mounted to a wall, floor, ceiling or any otherflat surface in a catheter lab. The receiver plate 904 is configured toreceive the mount plate 902 and hold it in place via magnetic force.

FIG. 10 is a diagrammatic perspective view of an angled mounting bracket1000 that is configured to couple to the hub 101. The angled mountingbracket 1000 includes a mounting surface 1002 that is configured to bereleaseably coupled to either the bottom mounting surface 202 or the topmounting surface 204 on the hub 101 via a set of mounting apertures thatalign with the mounting aperture on the hub. The angled mounting bracket1000 further includes an angled surface 1004 configured to fit flushagainst and releaseably couple to a right angled surface in a catheterlab or other medical environment. For instance, the angled mountingbracket 1000 may be affixed to a corner of a gas box disposed under apatient table.

FIG. 11A is a front view of the hub 101 in a fluid-resistantconfiguration. Specifically, as shown in FIG. 11A, a plurality ofprotective caps are disposed over the connectors on the front panel 210to prevent fluid or foreign substances from entering the connectors. Asmentioned above in association with FIGS. 2A and 2B, many of theconnectors on the front panel 210 are sealed to provide some resistanceagainst fluid ingress, but the illustrated caps provide furtherprotection. It is contemplated that the caps shown in FIG. 11A mayremain on their respective connectors during a patient procedure iftheir respective connectors are not in use. In the illustratedembodiment, the caps are commercially available from Souriau SAS, butalternatively, they may be any other type of cap configured to seal theconnectors on the hub 101. Each cap is physically configured to matewith a specific connector so that the resulting seal is water-tight. Forexample, a trapezoid-shaped dust cap 1100 is disposed over the VGAconnector 242. The dust cap 1100 includes a lanyard 1102 extending fromthe dust cap to the front panel 210. As another example, the fiber opticconnectors 224 and 226 include flip caps 1104 and 1106 that are mountedto the connectors on hinges. As such, the flip caps 1104 and 1106 may beflipped open when cables need to be connected to the fiber opticconnectors 224 and 226, and flipped close when the cables aredisconnected. As mentioned above, the USB connectors 240 are sealed andare fluid-resistant, and thus do not require extra protection. As yetanother example, in the illustrated embodiment of FIG. 11A, thecircular-shaped IVUS PIM connector 220 has a circular-shaped protectivecap 1108 disposed thereon. The protective cap 1108 is tethered to theconnector 220 via a flexible arm 1110.

Referring now to FIGS. 11B and 11C, FIG. 11B is a diagrammatic sectionalside view of the IVUS PIM connector 220 on the front panel of the hub101, and FIG. 11C is a diagrammatic perspective view of the protectivecap 1108. As noted above, the interface between the front interfacepanel 210 and the connector 220 is fluid resistant. This is due in partto a pair of complementary washers 1112 and 1114. The washers 1112 and1114 are disposed around the connector 220 on either side of the frontpanel 210 to create a fluid-resistant seal therebetween. As shown inFIG. 11C, the protective cap 1108 is configured to removeably mate withthe connector 220 to keep dust, fluid, and other particles out of theconnector. The cap 1108 includes an inner ring 1114 and an outer ring1116 that are configured to create a fluid-resistant seal when engagedwith the connector 220. The cap 1108 also includes a retaining portion1118 configured to fixedly engage an outside portion of the connector220. When so engaged, the cap 1108 is tethered to the connector 220 viathe flexible arm 1110. The cap 1108 is just one example of a protectivecap that may be used with the connectors on the hub 101 and other capsmay be used that are configured in a different manner, for instance, tomate with connectors with different shapes than the connector 220.

FIG. 12 is a functional block diagram of an embodiment of a poweredmedical communication hub. As shown in FIG. 2A, the hub 101 may includethe IVUS PIM connector 220, the functional measurement (FM) toolconnector 222, the first and second fiber optic connector 224 and 226,the OCT PIM connector 228, the bedside control surface connector 230,the FLIVUS PIM connector 232, the FLIVUS footswitch connector 234, theauxiliary power connector 236, the ECG/aortic device connector 238, theUSB connectors 240, and the VGA display connector 242. As shown in FIG.12, the IVIS PIM connector 220 is communicatively coupled to theprocessing system 120 via a link 1200. A cable 1202 transmitting power,ground, and data signals extends from the processing system 120 to thelink 1200, where the signals are internally forwarded to the IVUS PIMconnector 220. In some embodiments, the link 1200 and the connector 220may be integrated such that the cable 1202 running from the processingsystem 120 to the hub 101 extends through the aperture 214 in the rearpanel 212 (FIG. 3) and couples to one side of the connector 220/link1220, and a cable running from the IVUS PIM 112 to the hub 101 couplesto the other side of the connector 220. In other embodiments, however,the link 1200 may be integrated into the rear panel 212 such that thecable 1202 running from the processing system 120 to the hub 101 doesnot extend into the interior of the hub. The hub 101 further includes alink 1204 that communicatively couples the processing system 120 to theFM tool connector 222. A cable 1206 transmitting power, ground, and datasignals extends from the processing system 120 to the link 1204, wherethe signals are internally forwarded to the FM tool connector 222, whichforwards the signals to a connected FM tool, such as a FM Pimette 1207.Similar to the link 1200, the link 1204 may, in some embodiments, beintegrated into the FM connector 222 or, alternatively, it may bedisposed on the rear panel 212.

The hub 101 further includes a MultiFiber Push-On (MPO) link 1208 towhich the first and second fiber optic connectors 224 and 226 areinternally coupled. In general, the MPO link 1208 is configured toaggregate fiber optic signals and route them over a single fiber opticline. As shown in FIG. 12, a single fiber optic cable 1210 extends fromthe processing system 120, through the aperture 212 in the rear panel214, and to the MPO link 1208 where data destined for the first andsecond fiber optic connectors 224 and 226 is parsed and routed to theappropriate connector. In some embodiments, the MPO link 1208 may becoupled to a printed circuit assembly (PCA) disposed inside of the hub101 near the aperture 214, but, in other embodiments, the MPO link maybe disposed on the rear panel 212.

The hub 101 includes links 1212 and 1214 that respectivelycommunicatively couple the processing system 120 to the OCT PIMconnector 228 and the bedside control surface connector 230. Asmentioned above, the connectors 228 and 230 pass Ethernet-based datasignals to connected medical-sensing tools. Thus, in the illustratedembodiment, the links 1212 and 1214 are RJ45 jacks that respectivelyaccept Cat 5 e cables 1216 and 1218. However, in other embodiments, thelinks 1212 and 1214 may accept Ethernet-based data over coaxial, fiberoptic, or some other type of suitable cable. In some embodiments, thelinks 1212 and 1214 may be integrated into a PCA disposed within the hub101 and communicatively coupled to the connectors 228 and 230 viaconductive traces on the PCA, but, in other embodiments, the links 1212and 1214 may be disposed on the rear panel 212 for easy access. The hub101 further includes a link 1220 configured to communicatively couplethe processing system 120 to the ECG device connector 238, and thus theECG device 116. In some embodiments, the link 1220 may be integratedinto the ECG device connector 238 such that a ECG-signal cable 1222running from the processing system 120 to the hub 101 extends throughthe aperture 214 in the rear panel 212 and couples to one side of theconnector 238/link 1220, and a cable running from the ECG device 116 tothe hub 101 couples to the other side of the connector 238. But, inother embodiments, the link 1220 may be disposed on the rear panel 212such that the cable 1222 running from the processing system 120 to thehub 101 does not extend into the interior of the hub. Additionally, thehub 101 includes a link 1224 configured to communicatively couple theprocessing system 120 to the VGA connector 242 and pass videoinformation to the display 122. In the illustrated embodiment, the link1224 accepts a male VGA connector disposed on the end of a cable 1226coupled to the workstation 120. However, in other embodiments, the link1224 may be configured to accept other video-based connectors such as aDVI connector, an HDMI connector, a DisplayPort connector, or an S-Videoconnector. Similar to the links 1200, 1204, and 1220, the link 1224 may,in some embodiments, be integrated into the its associated connector 242or, alternatively, it may be disposed on the rear panel 212 for easyaccess.

The hub 101 further includes a link 1228 and a wireless communicationmodule 1230 that is operable to communicate with medical sensing-relatedtools in close proximity to the hub, such as a wireless-ready PIM. Inone embodiment, the wireless communication module 1230 may be a wirelesspersonal area network (WPAN) communication module such as an Ultra-wideband (UWB) module, a wireless FireWire module, or wireless USB module, aBluetooth module, a IEEE 802.11-based wireless module or some otherhigh-speed wireless module. In the illustrated embodiment, data passesover a data cable 1232 to link 1228, which forwards it to the wirelesscommunication module 1230 to be wirelessly transmitted. In someembodiments, the link 1228 may be a RJ45 connector through whichEthernet-based data passes, but in other embodiments it may be anothertype of connector through which Ethernet-based data may pass or maytransmit a different type of data. As with the links 1212 and 1214, thelink 1228 may be integrated into a PCA disposed inside of the hub 101 insome embodiments or it may be disposed on the rear panel 212 in otherembodiments.

Further, the hub 101 includes a remote extender 1234. In general, theremote extender 1234 is configured to extend the range of USBcommunications by converting USB-based data to fiber optic-based data sothat the data may be transported over long distances (e.g. up to 500meters). In the illustrated embodiment, the USB connectors 240 arecommunicatively coupled to the remote extender 1234, which is in turn,coupled to the MPO link 1208. As such, the processing system 120 maycommunicate with USB-based devices such an input device 1236 (e.g.joystick, mouse, keyboard, touchpad etc) even if the hub 101 is locatedhundreds of meters from the workstation. Additionally, the FLIUVS PIMconnector 232 is communicatively coupled to the remote extender 1234,and thus may pass USB-based data to the processing system 120 via thehub 101. Further, as shown in FIG. 12, the FLIVUS foot switch connector234 and the ECG device connector 238 are communicatively coupled to theFLIVUS connector 232 so that signals from a FLIVUS footswitch 1238 andthe ECG device 116 may be used to coordinate data collection by a FLIVUSPIM 1240 coupled to the connector 232.

The hub 101 includes a power distribution module 1242 configured todistribute power to medical sensing-related tools connected to the hub.In the illustrated embodiment, the power distribution module 1242 is ahardware-based module. However, in other embodiments, the module 1242may be a combination of hardware and software, in which softwarecontrols power flow through the hardware. In the illustrated embodiment,a link 1244 electrically couples the power distribution module 1242 to a48 volt DC medical-grade power supply in the workstation 120. In otherembodiments, however, the power distribution module 1242 may draw powerfrom another power source such as a wall receptacle. The powerdistribution module 1242 converts the power provided by the processingsystem 120 into a plurality of power amounts (i.e. levels), which areappropriately routed to various connectors in the hub 101. For instance,the power distribution module 1242 is electrically coupled to the firstand second fiber optic connectors 224 and 226 and provides them with 48volts DC. The power distribution module 1242 is also electricallycoupled to the OCT PIM connector 228, the bedside control surfaceconnector 230, the auxiliary power connector 236, and the FLIVUS PIMconnector 232 and respectively provides them with, 48 volts DC, 12 voltsDC, 24 volts DC, and 48 volts DC. Additionally, the power distributionmodule 1242 provides 12 volts DC to the wireless module and 5 volts DCto the remote extender 1234 which, in turn, supplies the USB connectors240 with 5 volts DC. In alternative embodiments, the power amountsdistributed to the connectors may vary. In further embodiments, thepower distribution module 1242 may be operable to determine the amountof power required by medical sensing-related tool connected to aconnector on the hub 101 and dynamically supply the correct amount ofpower. In yet further embodiments, the hub 101 may include a controllerto interrogate newly-connected medical sensing tools to determineoperational attributes such as voltage requirements. U.S. PatentApplication No. 61/473,625, entitled “MEDICAL SENSING COMMUNICATIONSYSTEM AND METHOD”, discloses a medical sensing communication systemthat includes a controller and power supply unit that are operable todynamically supply different medical sensing tools with differentamounts of power based on their needs and is hereby incorporated byreference in its entirety. In the illustrated embodiment, the processingsystem 120 provides the hub 101 with 48 volts DC via a power cable 1246that is coupled to the link 1244. In some embodiments, the link 1244 maybe coupled to a PCA disposed inside of the hub 101 near the aperture214, but, in other embodiments, the link 1244 may be disposed on therear panel 212 for easy access. Additionally, as shown in FIG. 12, thehub 101 may be electrically coupled to a ground line 1248 via a cable1250. Although not shown for purposes of clarity, the ground isdistributed to the various connectors on the front panel of the hub 101that draw power from the power distribution module 1242 so that theconnectors may pass along the ground to the connected tools.

As mentioned above, the front interface panel 210 (FIG. 2A) and theconnectors 220, 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and242 described above may together be considered a forward interfaceassembly. Further, the rear interface panel 212 (FIG. 3) and the links1200, 1204, 1208, 1212, 1214, 1220, 1224, 1228, and 1244 may togetherconsidered a rear interface assembly. Thus, as described above, in someembodiments the rear interface assembly may include internal portions ofthe hub 101 (e.g. when the links are integrated into a PCA disposedinside of the hub).

With reference now to FIGS. 1, 3 and 12, the rear interface assembly ofthe hub 101 may be assembled in the following manner. First, aftercables 1202, 1206, 1216, 1218, 1246, 1222, 1210, 1232, 1226, and 1250have been installed in trench 126 such that they enter the catheter lab102 through trench entry port 128, they may be threaded through acoupler, the flexible hose 124, and another coupler such as straightcoupler 262. With the rear panel 212 and/or housing removed from the hub101, the cables may then be threaded through the aperture 214 in therear panel 212 and coupled to their respective links inside of the hub101. For instance, the cables 1216 and 1218 may be coupled to the links1212 and 1214, which, in some embodiments, may be integrated into a PCAdisposed within the hub 101. Once every cable extending from theprocessing system 120 has been coupled to the hub 101, the rear panel212 may be fixedly secured to the hub 101 with connectors such asscrews. As noted above, when the rear panel 212 is coupled to the hub101, the gasket 213 creates a fluid-resistant interface between the two.Next, the coupler 262 may be fixedly coupled around the aperture 214 inthe rear panel 212 with connectors such as screws, and the flexible tube124 may be fixedly secured to coupler 262 on its hub-end and to anothercoupler on its trench-end. Once assembly is complete, the cablesconnecting the processing system 120 to the hub 101 and their associatedlinks inside of the hub are protected from damaging elements in thecatheter lab such as fluids and impact. One of ordinary skill in the artwould understand that the previous assembly scenario is simply oneexample and other scenarios using different elements and/or positioningmay be implemented.

FIG. 13 is a functional block diagram of a powered medical communicationhub 1300 according to another embodiment of the present invention. Thehub 1300 is similar to the hub 101 shown in FIG. 12 but differs inseveral aspects as described below. Specifically, the hub 1300 includesa Power-over-Ethernet (PoE) module 1302 communicatively interposedbetween the processing system 120 and the OCT PIM connector 228 and thebedside control surface connector 230. A shown in FIG. 13, a singleCat5e cable 1304 (or other Ethernet-compatible communication medium) mayextend from the processing system 120 to an Ethernet-based link 1306 inthe hub 1300. The link 1306, in turn, communicatively couples to the PoEmodule 1302, where packetized data is routed to the appropriateconnector. Further, the PoE module 1302 draws power (e.g. 48 volts DC)from the power distribution module 1242 and passes it to downstreamEthernet-based devices via the connectors 228 and 230. The downstreamdevices may, in turn, utilize the power as needed. In alternativeembodiments, the PoE module 1302 may draw power from the processingsystem 120 via link 1306 in addition to or instead of drawing power fromthe power distribution system 1242. Further, in the embodiment of FIG.12, the IVUS PIM connector 220 and FM tool connector 222 draw powerdirectly from their respective links 1200 and 1204, however, in theembodiment of FIG. 13, these connectors may draw power directly from thepower distribution module 1242. Additionally, in hub 1300, the ECGconnector 238 may draw power from the power distribution module 1242 aswell.

FIG. 14 is a schematic drawing depicting a medical sensing communicationsystem 1400 including a bedside utility box (BUB) 1401. The medicalsensing communication system 1400 is a network-connected, datacollection solution for multiple modality medical sensing. Generally, inthe system 1400, the BUB 1401 is a central hub that interconnects aplurality of medical sensing-related tools and facilitates communicationbetween the tools and a data network. In one embodiment, thecommunication system 1400 may be utilized to collect data from medicalsensing devices and transmit it to remote computing resources, where itis processed and returned. U.S. Provisional Patent Application No.61/473,570, entitled “MULTI-MODALITY MEDICAL SENSING SYSTEM AND METHOD”and filed on Apr. 8, 2011, discloses a computing resource capable ofprocessing multi-modality medical sensing data and is herebyincorporated by reference in its entirety.

In the illustrated embodiment, the medical sensing communication system1400 is deployed in a catheter lab 1402 having a control room 1404. Thecatheter lab 1402 includes a sterile field but its associated controlroom 1404 may or may not be sterile depending on the requirements of aprocedure and/or health care facility. The catheter lab and control roommay be used to perform on a patient any number of medical sensingprocedures such as angiography, intravascular ultrasound (IVUS), virtualhistology (VH), forward looking IVUS (FL-IVUS), intravascularphotoacoustic (IVPA) imaging, a fractional flow reserve (FFR)determination, a coronary flow reserve (CFR) determination, opticalcoherence tomography (OCT), computed tomography, intracardiacechocardiography (ICE), forward-looking ICE (FLICE), intravascularpalpography, transesophageal ultrasound, or any other medical sensingmodalities known in the art. For example, in catheter lab 1402 a patient1406 may be undergoing a multi-modality procedure, in which IVUS datawill be collected with an IVUS catheter 1408 and OCT data will becollected with an OCT catheter 1410. The IVUS catheter 1408 may includeone or more sensors such as a phased-array transducer. In someembodiments, the IVUS catheter 1408 may be capable of multi-modalitysensing such as IVUS and IVPA sensing. The OCT catheter 1410 may includeone or more optical sensors.

The communication system 1400 includes a number of interconnectedmedical sensing-related tools in the catheter lab 1402 and control room1404 to facilitate this multi-modality workflow procedure, including anIVUS patient isolation module (PIM) 1412, an OCT PIM 1414, anelectrocardiogram (ECG) device 1416, a bedside control surface 1418, acontrol room control surface 1420, and a boom display 1422. The BUB 1401in the catheter lab 1402 interconnects these medical sensing-relatedtools and communicatively couples them to a data network 1428. That is,the BUB 1401 is a central hub through which the tools in the catheterlab 1402 and control room 1404 connect to the data network 1428. In theillustrated embodiment, the data network 1428 is TCP/IP-based local areanetwork (LAN), however in other embodiments, it may utilize a differentprotocol such as Synchronous Optical Networking (SONET), or may be awide area network (WAN). Further, in another embodiment, the datanetwork 1428 may be a data bus network, such as a Universal Serial Bus(USB) network, for connecting BUB 1401 to a host controller withcomputing resources. The BUB 1401 will be described in greater detail inassociation with FIGS. 14-17.

In the illustrated embodiment of FIG. 14, the IVUS catheter 1408, PIM1412, and the BUB 1401 together may be considered a patientcommunication system that is operable to receive medical sensing datacollected from the patient 1406 by the IVUS catheter 1408 and totransmit the received data onto the data network 1428. As shown, the BUB1401 is communicatively coupled to the IVUS patient isolation module(PIM) 1412 via a wired connection such as a standard copper link or afiber optic link, and the IVUS PIM is, in turn, coupled to the IVUScatheter 1408 via a similar wired connection. In alternativeembodiments, however, the BUB-PIM connection and/or the PIM-catheterconnection may be wired or wireless. In one embodiment, the PIM 1412includes an analog to digital (A/D) converter and transmits digital datato the BUB 1401, however, in other embodiments the PIM transmits analogdata to the BUB. Further, in some embodiments, the PIM 1412 and BUB 1401communicate with a standardized data transmission protocol, such asSynchronous Optical Networking (SONET). Further, the PIM 1412 providespower to data collection sensors disposed on the catheter 1408 via itsconnection to BUB 1401. Typically, different sensory instruments requiredifferent amounts of power, and thus their associated PIMs may drawdifferent amounts of power from the BUB 1401. As discussed later, theBUB 1401 is operable to dynamically provide the appropriate amount ofpower to IVUS PIM 1412 via the wired connection.

Further, the OCT catheter 1410 and PIM 1414 may also be considered apart of the patient communication system that includes PIM 1412 and BUB1401. With the OCT catheter 1410 and PIM 1414 the patient communicationsystem is further operable to receive medical sensing data collected bythe OCT catheter 1410 and transmit the received data onto the datanetwork 1428. In the illustrated embodiment, the OCT PIM 1414 iscommunicatively coupled to BUB 1401 via a wireless connection, but inalternative embodiments, may be communicatively coupled via a wiredconnection. In one embodiment, the PIM 1414 includes an A/D converterand transmits digital data to the BUB 1401, however, in otherembodiments the PIM transmits analog data to the BUB. Further, in someembodiments, the PIM 1414 and BUB 1401 communicate with a standardizeddata transmission protocol, such as SONET. In some embodiments, the PIM1414 may include a battery to power catheter 1410, may draw power from awired power connection, or may be wirelessly powered.

For convenience purposes, the PIMs 1412 and 1414 may hang from thepatient table or may be placed in another location near the patient.Although two PIMs are depicted as communicatively coupled to the BUB1401, additional PIMs associated with different medical sensingmodalities may be connected to BUB 1401. Any such additional PIMs maycommunicate with the BUB 1401 concurrently with the PIMs 1412 and 1414.Still further, a single PIM may support multiple modalities, such asIVUS and IVPA. Additionally, in some embodiments, such as those in whichpatient data is collected using angiography, one of the illustrated PIMsmay be replaced with a C-arm. In such embodiments, the C-arm may act asthe power and data intermediary between the angiography sensors and thenetwork 1428. Still further, in another embodiment, the medical sensingcommunication system 1400 may include an adapter device to serve as anintermediary between a third-party system such as an angiography systemand the BUB 1401. Such an adaptor device may transform data in aproprietary third-party format into a format usable by the system 1400.U.S. Patent Application Publication No. US 2007/0232933, entitled“Component-Based Catheter Lab Intravascular Ultrasound System,”discloses a component-based IVUS system that includes a PIM and ishereby incorporated by reference in its entirety.

As mentioned above, the ECG device 1416 is also communicatively coupledto BUB 1401 via a wired or wireless connection. The ECG device 1416 isoperable to transmit electrocardiogram signals from patient 1406 to theBUB 1401. In some embodiments, the BUB 1401 may be operable tosynchronize data collection with the catheters 1408 and 1410 using theECG signals from the ECG 1416.

The bedside control surface 1418 is also communicatively coupled to theBUB 1401 and provides user control of the particular medical sensingmodality (or modalities) being used to diagnose the patient 1406. In thecurrent embodiment, the bedside control surface 1418 is a touch screenthat provides user controls and diagnostic images on a single surface.In alternative embodiments, however, the bedside control surface 1418may include both a non-interactive display and separate controls such asphysical buttons and/or a joystick. In the illustrated embodiment, thebedside control surface 1418 and BUB 1401 communicate over a wiredconnection such as a standard copper link or a fiber optic link but,alternatively, the control surface 1418 and BUB 1401 may communicatewirelessly. Further, in some embodiments, the bedside control surface1418 may also be communicatively coupled directly to one or both of PIMs1412 and 1414. The bedside control surface 1418 includes an integratedprocessing unit to drive a graphical user interface (GUI)-based workflowpresented on the touch screen. In an exemplary embodiment, theparticular GUI-based workflow presented by the bedside control surface1418 depends on the medical sensing modality being used to diagnose thepatient 1406. To this end, the bedside control surface 1418 is capableof displaying multiple GUI-based workflows, each corresponding to aparticular sensor or imaging modality or simultaneous combinationthereof. The bedside control surface 1418 is further operable to displayco-registration GUI-based workflows, for example, to integrate sensingdata collected by catheters 1408 and 1410. An API-based softwareframework executing on the bedside control surface 1418 manages themultiple workflows. U.S. Patent Application No. 61/473,591, entitled“Distributed Medical Sensing System and Method” and filed on Apr. 8,2011, discloses a bedside control surface that executes GUI-basedworkflows using a software framework and is hereby incorporated byreference in its entirety.

The control room control surface 1420 in the control room 1404 is alsocommunicatively coupled to the BUB 1401 and, as shown in FIG. 14, isadjacent to catheter lab 1402. In the illustrated embodiment, thecontrol room control surface 1420 and BUB 1401 communicate over a wiredconnection such as a standard copper link or a fiber optic link but,alternatively, the control surface 1420 and BUB 1401 may wirelesslycommunicate. In the current embodiment, the control room control surface1420 is similar to the bedside control surface 1418 in that it includesa touch screen, integrated processing unit, and multitude of GUI-basedworkflows corresponding to different medical sensing modalities. Duringa procedure, however, the control room control surface 1420 may be usedto carry out a different aspect of the procedure's workflow than thebedside control surface 1418. In alternative embodiments, the controlroom control surface 1420 may include a non-interactive display andstandalone controls such as a mouse and keyboard. Further, theprocessing unit of the control room control surface 1420 may be morepowerful than the processing unit of the bedside control surface 1418.

The system 1400 further includes the boom display 1422. The boom display1422 may include an array of monitors, each capable of displayingdifferent information associated with a medical sensing procedure. Forexample, during an IVUS procedure, one monitor in the boom display 1422may display a tomographic view and one monitor may display a sagittalview. In an embodiment as described in FIG. 17, the boom display 1422may be coupled directly to and driven by the BUB 1401. In otherembodiments, the boom display may also be operable to receive image datafrom the bedside control surface 1418 or the control room controlsurface 1420.

With reference now to FIG. 15, illustrated is an aspect of the medicalsensing communication system 1400. Specifically, FIG. 15 is adiagrammatic perspective view of the bedside utility box (BUB) 1401 ofFIG. 14. As mentioned above, the BUB 1401 is a hub through which themedical sensing-related tools communicate with data network 1428. Ingeneral, the BUB 1401 is operable to collect medical sensing data fromconnected medical sensing devices such as the IVUS PIM 1412 and OCT PIM1414 and send it to remote computing resources to be processed. Onceprocessed, the medical sensing data may be returned to the BUB 1401,where it is routed to the control surfaces 1418 and 1420 to be displayedand analyzed by clinicians.

The BUB 1401 includes a number of sockets to which the medicalsensing-related tools connect. In the illustrated embodiment, the BUB1401 includes an ECG socket 1430, an auxiliary power socket 1432, aFLIVUS foot switch socket 1434, a FLIVUS PIM socket 1436, an OCT PIMsocket 1438, two USB sockets 1440 and 1442, a display socket 1444, a FFRPIM socket 1446, a IVUS PIM socket 1448, and a network communicationsocket 1450. Referring to FIGS. 14 and 15, the ECG device 1416 maycouple to the ECG socket 1430, the IVUS PIM 1412 may couple to the IVUSPIM socket 1448, the bedside controller 1418 may couple to the USBsocket 1440, and the control room control surface may couple to the USBsocket 1442. The USB sockets 1440 and 1442 to which the control surfaces1418 and 1420 connect may alternatively be replaced with othershort-distance high-speed ports such as FireWire ports or Thunderboltports. Further, in some embodiments, the boom display 1422 may becoupled to the display socket 1444, which, in the current embodiment, isa VGA port, but may alternatively be a DVI port, S-video port,DisplayPort port, HDMI port, or other type of video display port.Additionally, the BUB 1401 may communicate with the network 1428 throughthe network communication socket 1450. In the illustrated embodiment,the network communication socket 1450 is an Ethernet port, butalternatively, it may be another type of network communication port suchas a fiber optic port. Or, if the network 1428 is a data bus network,the network communication socket 1450 may be a USB port, a InfiniBandport, a HyperTransport port, a Thunderbolt port, FireWire port, or otherdata bus port. In the illustrated embodiment, the sockets of BUB 1401providing connectivity to medical sensing-related tools are dedicated toa specific medical sensing modality and thus conform to a number ofdifferent form factors. However, in alternative embodiments, the socketsmay be substantially similar (i.e. are standardized). Further, althoughthe BUB 1401 includes certain sockets for specific medicalsensing-related tools, in other embodiments, it may include additionaland/or different sockets to connect medical sensing devices,controllers, and displays.

FIG. 16 is a functional block diagram of an embodiment of a bedsideutility box (BUB). As described in FIG. 15, the BUB 1401 may include theECG socket 1430, USB socket 1440 and 1442, and the IVUS PIM socket 1448,to which the ECG device 1416, bedside control surface 1418, control roomcontrol surface 1420, and IVUS PIM 1412 respectively connect. The BUB1401 also includes the display socket 1444 and network communicationsocket 1450, to which the boom display 1422 and network 1428respectively connect. For purposes of clarity, the other sockets of BUB1401 illustrated in FIG. 15 have been omitted from the functional blockdiagram of FIG. 16. The BUB 1401 further includes a wirelesscommunication module 1460 operable to communicate with medicalsensing-related tools in close proximity to the BUB, such as the OCT PIM1414. In one embodiment, the wireless communication module 1460 may be awireless personal area network (WPAN) communication module such as anUltra-wide band (UWB) module, a wireless FireWire module, or wirelessUSB module or some other high-speed wireless module.

The BUB 1401 further includes a controller 1462 and a communicationmodule 1464. In some embodiments, the controller 1462 may be a low-powermicrocontroller with integrated memory and peripherals (i.e. asystem-on-a-chip). However, in other embodiments, the controller may bea general-purpose, central processing unit (CPU). The controller 1462(i.e. control module) is operable, among other things, to route datafrom the sockets 1430, 1440, 1442, 1448 and the wireless communicationmodule 1460 to the communication module 1464, where it may betransmitted to the network 1428 via socket 1450. In the currentembodiment, the controller 1462 includes an analog to digital (A/D)converter which the controller may selectively utilize based on whetherdata incoming from a connected PIM is in analog or digital form. Forexample, the controller 1462 may convert analog data from a PIM todigital data before it is routed to the communication module 1464.Additionally, in some embodiments, the controller 1462 may be operableto associate identifying information with the medical sensing data as itis routed to the communications module 1464. More specifically, thecontroller 1462 may create a plurality of digital messages from theincoming analog or digital data stream, where each message contains aportion of the digitized medical sensing data and a header. Theaforementioned U.S. Patent Application No. 61/473,591, entitled“Distributed Medical Sensing System and Method,” discloses creatingmessages that associate identifying information with medical sensingdata in more detail.

Further, in the event that multiple medical sensing devices are coupledto the BUB 1401, as illustrated in FIG. 16, the controller 1462 may beoperable to facilitate time synchronization among the devices forco-registration purposes. For instance, in one embodiment, thecontroller 1462 may be operable to serve as a master time server for thePIMs 1412 and 1414 using a network-based time synchronization protocolsuch as the Precision Time Protocol (PTP) or the Network Time Protocol(NTP). In another embodiment, the controller 1462 may be operable toassign a common timestamp to data as it arrives into the BUB 1401 from aplurality of medical sensing devices. Further, in another embodiment,the controller 1462 may communicate with connected medical sensingdevices using a synchronous protocol such as Synchronous OpticalNetworking (SONET), and may assign timestamps to incoming medicalsensing data based on the multiplexed communication. Still further, inother embodiments, the BUB 1401 may include a dedicated real-time clockto synchronize sampling by connected medical sensing devices. In such anembodiment, the real-time clock may distribute a synchronization signalto connected sensing devices and also the controller 1462 which may actas a co-registration processor. In some embodiments, the real-time clockmay be integrated into the controller 1462. The aforementioned U.S.Patent Application No. 61/473,591, entitled “Distributed Medical SensingSystem and Method,” discloses temporally synchronizing medical sensingdata collection in more detail.

Further, in some embodiments, the controller 1462 may be operable tomodify the medical data received from the medical sensing devices as itis routed to the communication module 1464. For example, in someembodiments, the controller 1462 may compress the data before it istransmitted over the network 1428. In this manner, large data setsproduced by imaging modalities such as OCT may be more efficiently movedover the network 1428. In some embodiments, the controller 1462 may alsobe operable to filter incoming sensing data in some manner.

The communication module 164 in the BUB 1401 is a high-speedcommunication module operable to transmit data received from the medicalsensing-related tools connected to the BUB 1401 and the network 1428. Inembodiments in which the network 1428 is packet-based, the communicationmodule 1464 is operable to packetize medical sensing data routed by (andpossibly digitized by) the controller 1462, address the resultingpackets, and the send the packets out over the network 1428. In theembodiments in which the controller 1462 segments incoming sensing datainto messages, the communication module 1464 may encapsulate themessages into TCP/IP packets for transmission over the network 1428. Inthe illustrated embodiment, the communication module 1440 is anEthernet-based communication module, however, in other embodiments thecommunications module may be a InfiniBand switched fabric communicationsmodule, HyperTransport communication module, a fiber optic link module,a USB controller, a Thunderbird controller, a FireWire controller, ahigh-speed wireless module or some other high-speed communication moduleknown in the art.

The BUB 1401 further includes a graphics controller 1466 operable tooutput images to the display socket 1444. In the illustrated embodiment,the graphics controller 1466 is a graphics processing unit (GPU)independent of the controller 1462, but, in other embodiments, it may beintegrated into the controller 1462 or be a plug-in, off-the-shelfcomponent. Further, in some embodiments, the BUB 1401 may include aplurality of display sockets, where the graphics controller 1466 iscapable outputting distinct video signals to each. The graphicscontroller 1466 gives the BUB 1401 the capability to independentlyoutput images representative of medical sensing data received from theconnected medical sensing devices. In some embodiments, this capabilitymay be utilized to reduce network bandwidth requirements. For example,data associated with a medical sensing modality that requires minimalprocessing (e.g. FFR) may be processed by controller 1462 andimmediately output to a display via graphics controller 1466, therebyeliminating the need to send the data over the network 1428 to beprocessed. Further, to mitigate against lost connectivity with network1428 during a catheterization procedure, the graphics controller 1466may be used to perform some rudimentary image processing of incomingmedical sensing data. For example, if during an OCT procedure in whichthe BUB 1401 is receiving OCT data from OCT PIM 1414, the computingresources on network 1428 become unavailable, the controller 1462 andgraphics controller 1466 may be operable to perform some minimal imageprocessing on the OCT data and output rudimentary OCT images to thedisplay boom 1422. Further, in some embodiments, the BUB 1401, uponreceiving medical sensing data, may render basic image data withgraphics controller 1466 and simultaneously transmit an unprocessedversion of the medical data to computing resources on network 1426 formore advanced processing and storage. A software framework executing onthe controller 1462 in the BUB 1401 manages the routing, analog todigital conversion, and image processing of incoming medical sensingdata. This software framework will be discussed in greater detail inassociation with FIG. 17.

The BUB 1401 further includes a medical-grade power supply unit (PSU)1468. The PSU 1468 provides power to the controller 1462, wirelessmodule 1460, and the medical sensing-related tools (e.g. medical sensingdevices, control surfaces) connected to the sockets 1430, 1440, 1442,and 1448. As mentioned above, different connected tools may havedifferent power requirements. For example, a phased-array catheter foruse in IVUS procedures may require more power than a pressure sensormounted on the distal end of a guide wire for use in a FFR procedure.Thus, in the current embodiment, the PSU 1468 is a multi-stage powersupply that includes an isolating transformer to step down an input ACvoltage and a plurality of switching power converters (PC) 1470, 1472,1474, 1476 to dynamically output a desired voltage at a specific socket.For example, the PSU 1468 may step down a 120V AC supply to anintermediate DC voltage and then each power converter (i.e. powermodule) may convert the intermediate voltage to one of a plurality of DCvoltages such as 48V, 24V, 12V, 5V, and 3.3V. The specific voltageoutput to each socket dynamically depends on the specific powerrequirements of the medical sensing-related tool connected. In oneembodiment, the PCs 1470, 1472, 1474, 1476 may be physically integratedinto the PSU 1468. In other embodiments, the PSU 1468 may be a differenttype of power supply known in the art and power conversion anddistribution may be done by other methods known by those of ordinaryskill in the art.

Additionally, upon connection of a medical sensing-related device to oneof the sockets 1430, 1440, 1442, and 1448, the controller 1462 isoperable to automatically interrogate the tool to determine connectionattributes such as voltage and communication protocol. In the currentembodiment, the controller 1462 utilizes a low-voltage (e.g. 5V) TTLlogic initialization process to communicate with a newly connectedmedical sensing tool. In alternative embodiments, however, a differenttype of initialization process may be used. After the initializationprocess is complete, the controller 1462 is operable to dynamically setthe voltage output to the tool and, in some embodiments, the protocolwith which the tool communicates with the BUB 1401.

Note that the functional block diagram shown in FIG. 16 has beensimplified for the sake of clarity. A person of ordinary skill in theart would understand that elements of the BUB 1401 may be rearranged orcombined and that additional elements may be added without changing thefunctionality described herein. Further, a person of ordinary skill inthe art understands that in the context of the current disclosure, amodule may refer to a hardware module, a software module, or acombination software and hardware module.

With reference now to FIG. 17, illustrated is a functional block diagramof the software framework executing on the BUB 1401. More specifically,FIG. 17 illustrates one embodiment of the medical sensing communicationsystem 1400 in which the IVUS PIM 1412, the OCT PIM 1414, an angiographysystem 1480, the bedside controller 1418, the boom display 1422, anddata network 1428 are communicatively coupled to the BUB 1401. Asmentioned above, the BUB 1401 includes a software framework to route,digitize, and process medical data received from connected medicalsensing devices. The software framework includes a plurality of softwarelayers that manage various aspects of the BUB 1401. For instance, anoperating platform 1482 undergirds the software framework and providesthe core functionality of the BUB 1401. For instance, the operatingplatform 1482 may manage power consumption and distribution of the BUB1401 and may also manage network connectivity. Further, the softwareframework may include an analog to digital conversion engine 1484operable to digitize analog data incoming from medical sensing devices,also may include a video engine 1486 operable to render images and videoassociated with medical sensing data. Additionally, the softwareframework includes a routing manager 1488 operable to control therouting of data between the medical sensing-related tools connected toBUB 1401 and the network 1428. In some embodiments, the routing managermay be operable to create a plurality of messages from digitized sensingdata, where each message includes identifying information about theassociated data.

Each of the software layers 1482, 1484, 1486, and 1488 additionallyexpose application programming interfaces (APIs) through which systemresources may be accessed. The software framework in BUB 1401 includes aprocessing application layer 1490 in which processing applicationsassociated with specific medical sensing modalities may execute.Utilizing the APIs exposed by the underlying software layers, theprocessing applications in the application layer 1490 may be operable torender video or other images (e.g. FFR signal traces) from the rawmedical sensing data transmitted to the BUB 1401 by connected medicalsensing devices. For example, if the BUB 1401 loses network connectivitywith the network 1428, an IVUS processing application in the applicationlayer 1490 may call video processing APIs exposed by the video engine1486 to render IVUS video images for display on the boom display 1422.Further, in some embodiments, the application layer 1490 may includeco-registration applications, in which medical sensing data from aplurality of medical sensing devices is co-registered and processed toproduce co-registration images for display via the boom monitor 1422.For instance, a co-registration application may display anelectrocardiogram (ECG) wave adjacent to IVUS imaging data. In anexemplary embodiment, additional processing applications may be added tothe application layer 1490 to support new medical sensing modalities orco-registration techniques developed after the BUB 1401 has beendeployed. Further, the API-based software framework allows theapplications 1490 to be independent of the supporting software layersand thus written by third parties to control custom workflows.

Referring now to FIG. 18, shown is a schematic drawing depicting amedical sensing communication system 1500 according to anotherembodiment of the present disclosure. The medical sensing communicationsystem 1500 is similar to the medical sensing communication system 1400shown in FIG. 14 Like medical sensing communication system 1400, medicalsensing communication system 1500 may be utilized to collect data frommedical sensing devices in catheter room 1402 and transmit it to remotecomputing resources, where it is processed and returned. However, insystem 1500, medical sensing devices collect and transmit medicalsensing data to remote computing resources without the use of a bedsideutility box (BUB).

In more detail, the patient 1406 may be undergoing a multi-modalityprocedure, in which IVUS data will be collected with the IVUS catheter1408 and OCT data will be collected with the OCT catheter 1410. In thesystem 1500, the IVUS catheter 1408 is communicatively coupled to anIVUS PIM 1502. As mentioned above, the IVUS catheter 1408 may be capableof multi-modality sensing such as IVUS and IVPA, and PIM 1502 maylikewise capable of receiving multi-mode sensor outputs. Without a BUBin system 1500, the IVUS PIM 1502 may itself be considered a patientcommunication system that is operable to receive medical sensing datacollected by the IVUS catheter 1408 and transmit the received data ontothe data network 1428. As such, the PIM 1502 is operable to performsimilar functions that the PIM 1412 and BUB 1401 performed together inthe patient communication system of FIG. 14. As shown, IVUS PIM 1502 iscoupled to the IVUS catheter 1408 via a wired connection. In alternativeembodiments, however, the PIM-catheter connection may be wired orwireless. In the illustrated embodiment, the PIM 1502 includes an analogto digital (A/D) converter and transmits digital data to the network1428 via a wired connection. The IVUS PIM 202 will be described ingreater detail in association with FIG. 19.

The medical sensing communication system 1500 further includes a OCT PIM1504 configured to receive OCT data from the OCT catheter 1410. Like theIVUS PIM 1502, the OCT PIM 1504 may itself be considered a patientcommunication system in the absence of a BUB. The OCT PIM 1504 isoperable to receive medical sensing data collected by the OCT catheter1410 and transmit the received data onto the data network 1428. Asshown, OCT PIM 1504 is coupled to the OCT catheter 1410 via a wiredconnection. In alternative embodiments, however, the PIM-catheterconnection may be wired or wireless. In the illustrated embodiment, thePIM 1504 includes transmits digital data to the network 1428 via awireless connection, such as an IEEE 802.11 Wi-Fi connection or anotherhigh-speed wireless connection.

The medical sensing communication system 1500 further includes a bedsidecontrol surface 1506. The bedside control surface 1506 may be similar tothe bedside control surface 1418 of FIG. 14 in that it provides usercontrol and displays images of the particular medical sensing modality(or modalities) being used to diagnose the patient 1406. However, in thecurrent embodiment, the bedside control surface 1506 communicates withthe network 1428 via a wireless connection, such as an IEEE 802.11 Wi-Ficonnection or another high-speed wireless connection. The bedsidecontrol surface 1506 is operable to wirelessly transmit workflow controlinformation to the PIMs 1502 and 1504 via the network 1428 and alsoreceive medical sensing data from the PIMs that has been processed byremote computing resources on the network 1428. Because the bedsidecontrol surface 1506 is wireless, it may be moved to a control room,different catheter room, or even a doctor's office as needed. Althoughtwo PIMs are depicted as part of system 1500, additional PIMs associatedwith different medical sensing modalities may be integrated in to system1500 and communicatively coupled to the network 1428 without the use ofa BUB.

FIG. 19 is a functional block diagram of an embodiment of the IVUS PIM1502 of FIG. 18. As described in FIG. 18, the PIM 1502 iscommunicatively coupled to both the IVUS catheter 1408 and the network1428 and is operable to route medical sensing data from the catheter tocomputing resources on the network. The PIM 1502 includes a socket 1510to which the catheter 1408 connects. The socket 1510 may be a dedicatedIVUS port or may be a standardized port such that any catheter with amatching standardized connector may connect to it. The PIM 202 furtherincludes a controller 1512 operable to route data from the socket 1510through an A/D converter 1514 and to a communications module 1516. Insome embodiments, the controller 1512 may be similar to the low powercontroller 1462 in the BUB 1401 of FIG. 16. As the PIM 1502 is oftenplaced near or on a patient during a procedure, it ideally gives offlittle or no heat in some embodiments. Alternatively, in someembodiments, the controller 1512 is coupled to a heat sink thatdisperses heat generated by the controller. Alternatively, the BUB 1401may include active cooling elements to prevent heat buildup. Further,the controller 1512 is operable to digitize analog data received fromthe IVUS catheter 1408 with the A/D converter 1514. Although, the A/Dconverter is depicted as an independent hardware module, in someembodiments, the A/D converter may be a software module executing on thecontroller 1512. Additionally, in some embodiments, the data receivedfrom a catheter may already be digitized and thus controller 1512 maydisable the A/D converter 1514.

Further, after incoming medical sensing data has been digitized, thecontroller 1512 routes it to the communication module 1516, which may besimilar to the communication module 1464 in the BUB 1401 of FIG. 16. Insome embodiments, the controller 1512 may be operable to associateidentifying information with the medical sensing data as it is routed tothe communications module 1516. More specifically, the controller 1512may create a plurality of digital messages from the incoming analog ordigital data stream, where each message contains a portion of thedigitized medical sensing data and a header. The aforementioned U.S.Patent Application No. 61/473,591, entitled “Distributed Medical SensingSystem and Method,” discloses creating messages associating identifyinginformation with medical sensing data in more detail. Further, in someembodiments, the controller 1512 may be operable to modify the medicaldata received from the medical sensing devices as it is routed to thecommunication module 1516. For example, in some embodiments, thecontroller 1512 may compress the data before it is transmitted over thenetwork 1428. In some embodiments, the controller 1512 may also beoperable to filter incoming sensing data in some manner.

In embodiments in which the network 1428 is packet-based, thecommunication module 1516 is operable to packetize medical sensing datarouted by (and possibly digitized by) the controller 1512, address theresulting packets, and the send the packets out over the network 1428via a socket 1518. In the embodiments in which the controller 1512segments incoming sensing data into messages, the communication module1512 may encapsulate the messages into TCP/IP packets for transmissionover the network 1428. In some embodiments, the PIM 1502 may wirelesslytransmit unprocessed medical sensing data to the network 1428 like PIM1504, and, as such, the communication module 1516 may be a wirelesscommunication module. The PIM 1502 further includes a medical-gradepower supply unit (PSU) 1520. The PSU 1520 provides power to thecontroller 1512, wireless module 1516, and the phased-array transducersdisposed on catheter 1408 via the catheter's connection to socket 1510.In some embodiments, the PSU 1520 may be able to dynamically delivervarying amounts of power to socket 1510 based on the type of cathetercoupled to socket 1510. For instance, the PSU may include asecondary-stage switching power converter similar to the powerconverters in the BUB 1401 of FIG. 16.

Although illustrative embodiments have been shown and described, a widerange of modification, change, and substitution is contemplated in theforegoing disclosure and in some instances, some features of the presentdisclosure may be employed without a corresponding use of the otherfeatures. For example, in some embodiments, the medical sensingcommunication system 100 may be used to process non-cardiovasculardiagnostic data such as data from cranial or peripheral arteries, aswell as data from non-vascular body portions. Further, the system 100may be used to collect and process MRI data, or may be utilized incomputer assisted surgery (CAS) applications. And, as such, the hub 101may be configured to communicatively couple medical tools related tonon-cardiovascular diagnostic data collection and analysis to a remoteprocessing system. In this regard, the hub 101 may include any number ofdifferent and/or additional connector types, links, and internal modulesrelated to any number of medical fields. Further, any number ofadditional mounting brackets may be coupled to the hub 101 to positionit in any number of positions within a medical procedure room orlaboratory. Similarly, in some embodiments, the medical sensingcommunication system 1400 may be used to process non-cardiovasculardiagnostic data such data from cranial or peripheral arteries, as wellas data from non-vascular body portions. Further, the system 1400 may beused to collect and process MRI data, or may be utilized in computerassisted surgery (CAS) applications. It is understood that suchvariations may be made in the foregoing without departing from the scopeof the present disclosure. Accordingly, it is appropriate that theappended claims be construed broadly and in a manner consistent with thescope of the present disclosure. It is understood that such variationsmay be made in the foregoing without departing from the scope of thepresent disclosure. Accordingly, it is appropriate that the appendedclaims be construed broadly and in a manner consistent with the scope ofthe present disclosure.

What is claimed is:
 1. A patient communication system comprising: a first medical sensing device operable to collect first medical data associated with a first modality; an analog to digital converter communicatively coupled to the first medical sensing device and operable to digitize the first medical data; a network communication module communicatively coupled to the first medical sensing device and a data network, the network communication module operable to transmit the digitized first medical data onto the data network; a controller communicatively coupled to the analog to digital converter and the network communication module and operable route the first medical sensing data to the network communication module; and a power source operable to provide power to the first medical sensing device, the controller, and the network communication module.
 2. The patient communication system of claim 1, including a hub having therein the analog to digital converter, controller, and network communication module; and including a first patient isolation module communicatively coupled to the first medical sensing device and the hub and operable to receive the first medical data from the first medical sensing device and transmit the first medical data to the hub, the first patient isolation module being further operable to route power from the power source to the first medical sensing device.
 3. The patient communication system of claim 2, including a second medical sensing device operable to collect second medical data associated with a second modality different from the first modality; and including a second patient isolation module communicatively coupled to the hub and operable to receive the second medical data from the second medical sensing device and transmit the second medical data to the hub, the second patient isolation module being further operable to route power from the power source to the second medical sensing device.
 4. The patient communication system of claim 3, wherein the power source is operable to dynamically provide a first amount of power to the first patient isolation module based upon a power requirement of the first medical sensing device and dynamically provide a second amount of power to the second patient isolation module based upon a power requirement of the second medical sensing device, the first amount of power being different from the second amount of power.
 5. The patient communication system of claim 3, wherein the controller is operable to process the first medical data using a first processing application associated with the first modality to produce first processed medical data and is operable to process the second medical data using a second processing application associated with the second modality to produce second processed medical data.
 6. The patient communication system of claim 3, wherein the controller is operable to process the first and second medical data using a co-registration processing application to produce co-registered medical data.
 7. The patient communication system of claim 1, including a patient isolation module communicatively coupled to the first medical sensing device, the patient isolation module including the analog to digital converter, controller, and network communication module.
 8. The patient communication system of claim 1, wherein the power source is operable to dynamically provide an amount of power to the first medical device, the amount of power being based upon power requirements of the first medical sensing device.
 9. The patient communication system of claim 1, including a graphics controller communicatively coupled to the controller; wherein the controller is operable to process the first medical data using a processing application associated with the first modality to produce first processed medical data; and wherein the graphics controller is operable to drive the first processed medical data to a display.
 10. The patient communication system of claim 9, wherein the processing application is one of a plurality of processing applications executable by the controller, the plurality of processing applications including processing applications associated with modalities different from the first modality.
 11. The patient communication system of claim 1, wherein the medical sensing device includes a catheter configured to enter into a vessel of a body.
 12. The patient communication system of claim 11, wherein the catheter includes a sensor configured for at least one of intravascular ultrasound (IVUS) imaging, optical coherence tomography (OCT) imaging, a fractional flow reserve (FFR) determination, forward looking IVUS (FLIVUS) imaging, and intravascular photoacoustic (IVPA) imaging.
 13. The patient communication system of claim 1, wherein the network communication module is wirelessly communicatively coupled to the first medical sensing device.
 14. The patient communication system of claim 1, wherein the network communication module wirelessly communicatively coupled to the data network.
 15. A method of collecting medical sensing data, comprising: collecting, with a first medical sensing device, first medical data associated with a first modality; digitizing, with an analog to digital converter, the first medical data; routing, with a controller communicatively coupled to the analog to digital converter, the digitized first medical data to a network communication module; transmitting, with the network communication module communicatively coupled to a data network, the digitized first medical data onto the data network; and providing power, with a power source, to the first medical sensing device, the controller, and the network communication module.
 16. The method of collecting medical sensing data of claim 15, wherein the digitizing with the analog to digital converter, the routing with the controller, the transmitting with the communication module, and the providing power with the power source are performed by a hub communicatively coupled to the first medical device; and wherein the collecting first medical data includes transmitting the first medical data through a first patient isolation module to the hub.
 17. The method of collecting medical sensing data of claim 16, including collecting, with a second medical sensing device, second medical data associated with a second modality; including transmitting the second medical data through a second patient isolation module to the hub; including digitizing, with the analog to digital converter, the second medical data; including routing, with the controller, the digitized second medical data to the network communication module; including transmitting, with the network communication module, the digitized second medical data onto the data network; and including providing power, with the power source, to the second medical sensing device.
 18. The method of collecting medical sensing data of claim 17, wherein the providing power to the first medical sensing device includes dynamically providing a first amount of power to the first patient isolation module based upon a power requirement of the first medical sensing device; and wherein the providing power to the second medical sensing device includes dynamically providing a second amount of power to the second patient isolation module based upon a power requirement of the second medical sensing device, the first amount of power being different from the second amount of power.
 19. The method of collecting medical sensing data of claim 17, including processing, with the controller, the first medical data using a first processing application associated with the first modality to produce first processed medical data; and including processing, with the controller, the second medical data using a second processing application associated with the second modality to produce second processed medical data.
 20. The method of collecting medical sensing data of claim 17, including processing, with the controller, the first and second medical data using a co-registration processing application to produce co-registered medical data.
 21. The method of collecting medical sensing data of claim 15, wherein the digitizing with the analog to digital converter, the routing with the controller, the transmitting with the communication module, and the providing power with the power source are performed by a patient isolation module communicatively coupled to the first medical device; and wherein the collecting first medical data includes transmitting the first medical data to the patient isolation module.
 22. The method of collecting medical sensing data of claim 15, wherein the providing power to the first medical sensing device includes dynamically providing an amount of power to the first medical sensing device based upon a power requirement of the first medical sensing device.
 23. The method of collecting medical sensing data of claim 15, including processing the first medical data using a processing application associated with the first modality to produce first processed medical data; and including outputting, with a graphics controller, the first processed medical data to a display.
 24. The method of collecting medical sensing data of claim 23, wherein the processing application is one of a plurality of processing applications executable by the controller, the plurality of processing applications including processing applications associated with modalities different from the first modality.
 25. The method of collecting medical sensing data of claim 15, wherein the collecting the first medical data includes receiving medical data collected by introducing a catheter into a vessel of a body.
 26. The method of collecting medical sensing data of claim 25, wherein the first medical data includes at least one of intravascular ultrasound (IVUS) imaging data, optical coherence tomography (OCT) imaging data, fractional flow reserve (FFR) data, forward looking IVUS (FLIVUS) imaging data, and intravascular photoacoustic (IVPA) imaging data. 